home *** CD-ROM | disk | FTP | other *** search
- Path: nntphub.cb.att.com!not-for-mail
- From: rmb@hercules.cb.att.com (59532-Richard M Brack(CB2008)000)
- Newsgroups: comp.sys.amiga.networking
- Subject: Re: Announce: AWeb 1.0 released!
- Date: 1 Apr 1996 17:13:18 GMT
- Organization: AT&T
- Message-ID: <4jp2re$1pr@nntpb.cb.att.com>
- References: <4iva78$5pa@news.xs4all.nl> <19960326.79D3B98.696F@polaris.org.au> <19960329.7971A10.9D2D@contessa.phone.net> <paul.4cbx@serena.iaehv.nl>
- NNTP-Posting-Host: herc-fddi.cb.att.com
-
- In article <paul.4cbx@serena.iaehv.nl>,
- Paul Kolenbrander <paul@serena.iaehv.nl> wrote:
- >On Fri, 29 Mar 96, Mike Meyer typed the following line(s):
- >
- >> There is at least one bug in AWeb's HTML 2.0 support. It will
- >> sometimes format this ugly construct:
- >>
- >> <FONT SIZE=+1>G</Font>et <FONT SIZE=+1>O</Font>ur <FONT SIZE=+1>G</Font>reat
- >> <FONT SIZE=+1>P</Font>roduct <FONT SIZE=+1>N</Font>ow
- >>
- >> As:
- >>
- >> Get Our Great Product N
- >> ow
- >
- >I disagree with you here. There is nothing wrong with AWeb's HTML 2.0
- >support. Especially as the <FONT></FONT> tag pair is NOT a part of the
- >HTML 2.0 standard. But is one of the NetScape custom tags. BTW, have
-
- I thought the same thing at first, but think about it... Any tags that
- are not understood should be ignored. AWeb is ignoring the <FONT></FONT>
- tags in that it's not mucking with the fonts. But there is no space
- in '<FONT SIZE=+1>N</Font>ow' so it should be treated as a single word
- with no breaks. So AWeb is not correctly ignoring an unsupported tag,
- as it should be.
-
- I don't think I've run into this myself, I'm just going by what the
- original poster said. So far, I enjoy AWeb the most of the Amiga
- browsers...
-
-
- rich...
- rmb@hercules.cb.att.com
-
-
-